Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 58.80%. Comparing base (08c9bc4) to head (5824715).
Report is 20 commits behind head on main.

@@             Coverage Diff             @@
##             main      #76       +/-   ##
===========================================
- Coverage   69.97%   58.80%   -11.17%     
===========================================
  Files           2        2               
  Lines         403      403               
  Branches       26       87       +61     
===========================================
- Hits          282      237       -45     
  Misses        100      100               
- Partials       21       66       +45     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

This might have been too eager, I am fine with just one library but maybe we need to continue using the SONAME variable?

Warning: pkg(8) will not register it as being provided by the port.
Warning: If another port depend on it, pkg will not be able to know where it comes from.
Warning: It is directly in /usr/local/lib, it is probably used by other ports.```

A SONAME is only required when linking via a libnss_cache.so symlink, so that the linker writes libnss_cache.so.2 into the binary rather than the path name. We're not providing such a symlink, so it is not necessary. If someone were to link to the library for some reason, that would require passing using the full path (rather than using -lnss_cache), in which case the linker records that path correctly.

A SONAME is only required when linking via a libnss_cache.so symlink, so that the linker writes libnss_cache.so.2 into the binary rather than the path name. We're not providing such a symlink, so it is not necessary. If someone were to link to the library for some reason, that would require passing using the full path (rather than using -lnss_cache), in which case the linker records that path correctly.

Empirically it seems to be used by the pkg system. Can it not be set to the same file name?

Who even are the people that approved and merged this with no history with the repo. Typical abysmal Google engineering quality...

This is a standard Debian lint as well https://lintian.debian.org/tags/sharedobject-in-library-directory-missing-soname.html